This repository was archived by the owner on Jun 18, 2024. It is now read-only.
Use Prose.io for editing, rather than the the project's fork #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Project open data launched using http://project-open-data.github.io/contribute for editing due to two upstream issues (prose/prose#403, and prose/prose#389).
Now that Prose v1.0 is out, rather than maintain our own fork, it would make sense to have the 📝 button point_right: directly to http://prose.io.
Prose.io hosts prose v1, which is a complete overhaul and includes:
I believe it to be significantly more user friendly (:computer:), and as a free service (:moneybag:), requires no action or upkeep on our part (:wrench:). Prose would require the user to :key: with their :octocat: account (as they do now with our fork), but all subsequent requests will be directly to from the user's browser to the GitHub API, minimizing the risk of any information or activity being exposed to or altered by third-parties.
This pull request simply changes the variable in the config file from our fork to http://prose.io and should require no further action on our part once merged.